Purchasing >  Price lists >  Price list entry  

Display all Hide all

The definition of supplier price lists is comprised of four major stages:

  • the setup of the invoicing elements, defining the different invoice footers that can influence the price setting of a business partner (se the Invoicing elements documentation).
  • The setup of the structure codes, defining the different discount and charge columns that can be applied to a specific business partner (see the Price list structure documentation).
  • The price list code setup, defining the different price setting rules that can be applied to a structure code (see the Price list setup documentation).
  • The entry of the price list records, defining the values of the product price themselves and/or discounts and charges, for each price list code.

This function is thus the last stage in the price list definition. It is used to define, for each previously set up price list code, price list records mentioning the following elements:

  • the identifiers that will cause the price list to be applied (using the existing data in the called tables)
  • the application conditions (range in amount or in quantity...)
  • the gross price to be applied to the product
  • the amounts and/or rates of the discounts and charges

Consequently it is possible to create as many records as there are identifier combinations requiring the application of a specific price list (by price list code).

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

Presentation

The entry of the price list records is subdivided into two stages:

  • the selection of the price list code for which a price list record should be created
  • the entry of the price list database, or the modification of an already existing price list record.

 Selection of the price list code

Each record entered refers to a previously defined price list code. The requested price list code needs only to be selected in order to directly enter the entry of a linked price list record.

Entry of the price list database

The left list is used to select an already existing record. To create a new record, it is necessary to create a new document (tool bar or "File" menu).

The price list entry screen is subdivided into two parts:

Header information

The price list record activity, its application priority and the reason allocated to it are dependent upon the price list code. Thus they are not modifiable.

Nevertheless it is necessary to define:

  • a price list record code, as the record identifier.
  • a validity range, with dates that limit the application of the price list to a given period of time.
Lines button is enough.

The columns to be assigned are dependent upon the price list setup (Price list code). The various areas that can be displayed are described here below:

  • The identifiers 

the first columns always correspond to those identifiers defined in the criteria tab of the price list setup. There will be as many columns as there are defined identifiers.

The identifiers can only be the fields of the ITMMASTER, ITMBPS, BPARTNER, BPSUPPLIER, BPSUPPMVT, PPRICLINK tables. As a consequence they can only be assigned with values issued from these tables.

For instance: The identifier for a price list code X is the ITMREF field (Product) from the ITMMASTER table. If the ITMMASTER table only comprises two recordings, the BLUE and RED products, only the BLUE and RED values can be entered as identifiers in the "Product" column.

  • The currency

It is necessary to stipulate the currency on the line whenever an amount is subsequently entered (gross price, discount and/or charges in amount) in order to specify the currency of this amount subsequently entered.

This area can be initialized by the currency specified during price list code setup (Price tab).

  • The unit

This area can only be assigned when the unit is being used to calculate the gross price or as an application condition of the price list as a whole:

    • if the price is calculated based on an "n" quantity of equal units (dependent upon the price list code setup - if, in the Price tab, the "Price processing" field has the value "Value for n")
    • If some application conditions of the price list are defined as dependend upon a quantity of units (dependent upon the price list code setup - if, in the Price tab, the "Price/Qty" field is set to "Yes" or "Qty sections").
  • Minimum qty/Maximum qty - Minimum amount/Maximum amount

These areas can only be assigned if the price list code has been set up to limit the price list application based on:

    • a mini/maxi quantity of Purchase units (dependent upon the setup of the price list code - if, in the Price tab, the "Price/Qty" field is set to "Yes" or "Qty sections").
    • a cumulated mini/maxi quantity (dependent upon the setup of the price list code - if, in the Price tab, the "Price/Qty" field is set to "Qty sections").
  • Deadline

This area is optional. It is used to define a receipt lead-time for the product (potentially different according to the quantity sections or amount). This area allows the user to customize the reorder leadtimes based on the selection criteria defined for the price list (for instance: by suppliers, by product group...).

The leadtime mentioned in this area will make it possible to initialize the following elements in the purchase transactions:

    • either the planned receipt date, if the order date has been assigned (in order mode, for instance).
    • or the order date, if the receipt date has been assigned (in Purchase request mode, for instance).      

If no leadtime has been entered in the price list record, the system will look for the information at product record level (Purchase tab).

  • Price divisor

This area can only be assigned if the unit is used to calculate the gross price. The price calculation is then based on an "n" quantity of equal units. The value of the "Price divisor" corresponds to the unit quantity (dependent upon the setup of the price list code - if, in the Price tab, the "Price processing" field is set to "Value for n").

  • Prices

This field can only be assigned if the price list code has been set up to assign the unit price to the line (dependent upon the price list code setup - if, in the Price tab, the "price processing" field is set to "Value" or "Value for n").

  • Charges and discounts

These areas can only be assigned if the price list code is set up to take into account the discounts and charges defined at structure code level (dependend upon the price list code setup - Charges/discounts tab).

Close

 

Fields

The following fields are present on this tab :

Block number 1

Code used to identify the price list rule. A price list code identifies a parameterization giving access to the rules that determine the price, discounts or other elements linked to the price lists.

In order to parameterize a price list code, it is necessary to define its type, the list of fields used to identify when a price list line is applicable, and the list of fields assigned by the line. Once this parameterization is defined, the user has access to the price list line entry screens, where it is possible to enter both the criteria values and the corresponding values.

For instance: Definition of two discounts by Product group-Customer code combination. The Product group (coming from the product record) and Customer code (coming from the customer record) fields are considered as being the criteria during parameterization. The Discount1 category and Discount2 fields are the values assigned by the price list rule. In this case, the price list line entry screen contains four columns in all.

  • Price list record (field PLICRD)

Record number that allows the record to be identified in a unique way. This number is automatically generated or entered upon each creation of a price list record following the sequence number counter parameterization defined for the Sales price list records.

Block number 2

  • Priority (field PIO)

 
  • Active (field PLIENAFLG)

 

Block number 3

  • Validity start date (field PLISTRDAT)

Validity start date.
The right click (F4) is used to save the value entered in the field and to use it as initialization value for the following records.
  • Validity end date (field PLIENDDAT)

Validity end date.
The right click (F4) is used to save the value entered in the field and to use it as initialization value for the following records
  • Reason (field X1PRIREN)

 
  • field X2PRIREN

 
  • field PLIPRITYP

 

Grid

  • No. (field NUMLIG)

 
  • Criteria 1 (field CRIT1)

Criteria used to determine the prices and/or the sales conditions.
  • Criteria 2 (field CRIT2)

 
  • Criterion 3 (field CRIT3)

 
  • Criterion 4 (field CRIT4)

 
  • Criterion 5 (field CRIT5)

 

This is the currency code controlled in the currency table.
If the code is entered into the setup, it is displayed by default on the lines of the price list record. If necessary, it is initialized with the BP currency (when the BP is one of the criteria). This code can be modified.
  • PUR (field UOM)

On analytical inquiry, this field determines the non-financial unit linked to the displayed account.
The non-financial unit is determined when setting up an account associated with a given value.
This unit is called upon entry.
  • Minimum qty. (field MINQTY)

Minimum quantity for the assignment of this price list line.
This field can be specified only if the price list code has been set up to limit the application of the price lists according to a minimum quantity of purchase units (depends on the setup of the price list code - if in the Price tab, the "Price/Qty" field is set to "Yes" or "Qty sections").

When the line of the quote, the order, the delivery or the invoice is expressed in a different unit, this line is only used if this price list accepts the conversion of units.
For a grouped price list, the minimum quantity is compared with the quantity total of the lines meeting the criteria and displaying the same unit as the price list (or accepting the conversion of units).

 
  • Maximum qty. (field MAXQTY)

Maximum quantity for the assignment of this price list line.
This field can be specified only if the price list code has been set up to limit the application of the price lists according to a maximum quantity of purchase units (depends on the setup of the price list code - if in the Price tab, the "Price/Qty" field is set to "Yes" or "Qty sections").

When the line of the quote, the order, the delivery or the invoice is expressed in a different unit, this line is only used if this price list accepts the conversion of units.
For a grouped price list, the maximum quantity is compared with the quantity total of the lines meeting the criteria and displaying the same unit as the price list (or accepting the conversion of units).
  • Minimum amt. (field MINAMT)

Minimum value of the quote, order, delivery or invoice for the assignment of this price list line.
This information only concerns grouped price lists.
This field can be filled only if the price list code has been set up to limit the application of the price list according to a cumulated minimum price (depends on the setup of the price list code - if in the Price tab, the «Price/Qty» field has the value «Yes» or «Qty sections»).

The maximum value is compared with the totaled values for those lines meeting the criteria and displaying the same currency as the price list (or accepting the currency conversion).


 
  • Max amt (field MAXAMT)

Maximum value of the quote, order, delivery or invoice for the assignment of this price list line.
This information only concerns grouped price lists.
This field can be filled only if the price list code has been set up to limit the application of the price list according to a cumulated minimum price (depends on the setup of the price list code - if in the Price tab, the «Price/Qty» field has the value «Yes» or «Qty sections»).

The maximum value is compared with the totaled values for those lines meeting the criteria and displaying the same currency as the price list (or accepting the currency conversion).


 
  • Lead time (field LTI)

Time expressed in number of days that allows, from the order date, a planned reception date to be calculated.
  • Price fact (field PRIDIV)

Price divider used to define whether the price is expressed for a dozen products or a hundred etc.
  • Price (field PRI)

The price is always indicated with 4 decimals in order to ensure as much accuracy as possible for small amounts.
  • field XFRAREM1

 
  • field XFRAREM2

 
  • field XFRAREM3

 
  • field XFRAREM4

 
  • field XFRAREM5

 
  • field XFRAREM6

 
  • field XFRAREM7

 
  • field XFRAREM8

 
  • field XFRAREM9

 

Close

 

Reports

By default, the following reports are associated with this function :

  PRTSCR : Screen print

  PPRIC01 : Purchase pricing conditions C1

  PPRIC01P : Cond. purch pr lists C1 landscape

  PPRIC02 : Purchase pricing conditions C2

  PPRIC02P : Cond. purch pr lists C2 landscape

  PPRIC03 : Purchase price conditions

  PPRIC03P : Purchase price cond. landscape

This can be changed using a different setup.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation